Investigated and fixed workflow run #20579463931 which failed on Dec 29 after 12 consecutive successful runs. The failure occurred in the "Execute GitHub Copilot CLI" step of the agent job.

Root Cause

The 400 Bad Request error was caused by a oneOf JSON Schema constraint in the update_project tool schema that was inadvertently introduced in PR #8106. The Copilot CLI API does not support the oneOf keyword and returns a 400 Bad Request when encountering it in tool schemas.

Fix Applied

Removed the oneOf constraint from pkg/workflow/js/safe_outputs_tools.json and simplified the schema to use basic required fields:

Before:

{
  "inputSchema": {
    "type": "object",
    "properties": { ... },
    "oneOf": [
      {
        "required": ["project", "content_type", "content_number"],
        "properties": { "content_type": { "enum": ["issue", "pull_request"] } }
      },
      {
        "required": ["project", "content_type", "draft_title"],
        "properties": { "content_type": { "const": "draft_issue" } }
      }
    ]
  }
}

After:

{
  "inputSchema": {
    "type": "object",
    "required": ["project", "content_type"],
    "properties": { ... },
    "additionalProperties": false
  }
}

The conditional requirements (content_number vs draft_title based on content_type) are now handled by runtime validation in the JavaScript action scripts rather than JSON Schema validation.

Changes Made

• pkg/workflow/js/safe_outputs_tools.json: Removed oneOf constraint and added simple required: ["project", "content_type"]
• Recompiled workflows: All affected lock files updated with the fixed schema
• Verified: All unit tests pass

Impact

• The update_project tool schema is now compatible with Copilot CLI API
• Campaign orchestrator workflows can successfully execute without 400 Bad Request errors
• Runtime validation ensures proper field requirements based on content_type

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.